Working with Lighthouse Nodes
After Lighthouse is installed and configured, enroll a small set of nodes, then create a set of tags and node filters that allow nodes access to be filtered to the correct subset of users.
When these nodes are installed, test access to the Web UI and serial ports for the node.
Node Filters, Port Filters and Resource Filters can be associated with a group, this restricts the group to only have access to those resources which match the filter. Note that these filters intersect for ports and nodes, if you give a user access to a node but access to the first port on every node, they can only access the first port on that node, and they won't be able to access the first port on any other nodes. If no filter is assigned, and the user has permissions to access the object in question ("Connected Resource Gateway" for resources and "Node and Devices (Base) for Nodes and Ports), then the user has access to all objects. Those permissions are disabled by default when you create a new role.
Third-Party Nodes
A third-party node is any device that is not an Opengear node, and is enrolled via the Lighthouse Web UI. Lighthouse supports the following third-party nodes:
-
Generic third party devices
-
Avocent ACS6000
-
Avocent ACS8000
-
Avocent ACS Classic
-
Cisco 2900 Series
-
Digi Passport
-
Raritan Dominion
-
Lantronix SLC 8000
-
You can leverage the Connected Resource Gateway to proxy via SSH, HTTP or HTTPS to configure your third-party nodes. For more information about configuring your third-party nodes, see Set up Lighthouse as a Connected Resource Gateway (CRG).
- For Raritan and Avocent devices: For Lighthouse to recognize the ports as enabled, you must enable Direct Port Access (DPA) on each port in use on the device itself. This allows you to use the Web Terminal and SSH links to access devices that are connected to those ports directly from Lighthouse.